-
Notifications
You must be signed in to change notification settings - Fork 106
Review IPv4/IPv6 installation requirements #4213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Review IPv4/IPv6 installation requirements #4213
Conversation
|
The PR preview for 73f5632 is available at theforeman-foreman-documentation-preview-pr-4213.surge.sh The following output files are affected by this PR: |
ekohl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know it's a draft, but adding some notes for related work.
| * {Project} does not support configuring an HTTP proxy using a direct IPv6 address. | ||
| Instead, configure the HTTP proxy with a FQDN that resolves to the IPv6 address. | ||
| Using an IPv6 address as the HTTP proxy URL causes it to fail. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Katello/katello#11432 removes 1 bug in this area. I just don't know for sure if there aren't more lurking. I'd like to discuss this in the team to see if we can drop this text.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll keep this in for now, then, and please let me know if you find out it's safe to remove.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we can verify this works and resolve the bug then we can drop it for Foreman 3.16 and newer.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @ianballou, I see you approved the linked Katello PR. Do you know if it's safe to remove this bullet point?
951e8fc to
693c13e
Compare
693c13e to
2eae196
Compare
Co-authored-by: Maximilian Kolb <[email protected]>
maximiliankolb
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
style-wise LGTM
ekohl
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had a last look at it, but I see by now you merged it.
|
|
||
| The following requirements apply to installations in an IPv4 network: | ||
|
|
||
| * Ensure an IPv6 loopback is configured on the base system. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Style nit: I don't think you need ensure a requirement
| * Ensure an IPv6 loopback is configured on the base system. | |
| * An IPv6 loopback configured on the base system. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll style-nit you back: I'd prefer to keep this a full sentence (verb and all) to make the action item in the requirement clear. An option could be An IPv6 loopback must be configured on the base system. but that would introduce passive voice, which is frowned upon.
| Do not disable it. | ||
| * Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a blocker, but technically the requirement we have is IPv6 loopback. An implication of ipv6.disable=1 is that it disables this IPv6 loopback. You could argue it shouldn't be listed as a separate requirement but maybe more as an example for the "do not disable" line.
Would something like this work?
| Do not disable it. | |
| * Do not disable IPv6 in kernel by adding the `ipv6.disable=1` kernel parameter. | |
| Do not disable it. | |
| Use of the `ipv6.disable=1` kernel parameter or the `net.ipv6.conf.lo.disable_ipv6 = 1` sysctl option will break. |
I tried to avoid the duplicate "do not" on 2 lines just below each other.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| * {Project} does not support configuring an HTTP proxy using a direct IPv6 address. | ||
| Instead, configure the HTTP proxy with a FQDN that resolves to the IPv6 address. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm pretty sure this was a Katello-only limitation.
| * {Project} does not support configuring an HTTP proxy using a direct IPv6 address. | |
| Instead, configure the HTTP proxy with a FQDN that resolves to the IPv6 address. | |
| ifdef::katello,orcharhino,satellite[] | |
| * {Project} does not support configuring an HTTP proxy using a direct IPv6 address. | |
| Instead, configure the HTTP proxy with a FQDN that resolves to the IPv6 address. | |
| endif::[] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
* Merge all IPv4/IPv6 requirements into one module * Exclude a prereq on content from foreman-el/deb --------- Co-authored-by: Maximilian Kolb <[email protected]> (cherry picked from commit d7107ad)
What changes are you introducing?
Merging all the existing IPv4 and IPv6 sections with installation requirements into one module.
Why are you introducing these changes? (Explanation, links to references, issues, etc.)
This is part of preparing the installation prerequisites for the new installation guide in #4087
Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)
This is based on #3545 which didn't get merged then but now came in handy.
Contributor checklists
Please cherry-pick my commits into:
Review checklists
Tech review (performed by an Engineer who did not author the PR; can be skipped if tech review is unnecessary):
Style review (by a Technical Writer who did not author the PR):